-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: remove all receiver references to bundled config host files #229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
I think this does drive the host monitoring app's resource dataset which customers have complained about breaking before |
bceb622
to
4f27277
Compare
4f27277
to
088e3d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Infrastructure as Code | ![]() ![]() ![]() ![]() |
View in Orca |
![]() |
SAST | ![]() ![]() ![]() ![]() |
View in Orca |
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
![]() |
Vulnerabilities | ![]() ![]() ![]() ![]() |
View in Orca |
088e3d2
to
78f61a0
Compare
Good point! I put this receiver back and directed it at the agent config. I tested this locally with the otel app and it does work; it successfully tracks the host as a resource. |
@@ -160,7 +152,7 @@ receivers: | |||
storage: file_storage | |||
filestats/agent: | |||
collection_interval: 5m | |||
include: /etc/observe-agent/connections/common/base.yaml.tmpl | |||
include: /etc/observe-agent/observe-agent.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should always exist right? unless the user for some reason manually deletes it after install
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the expanded env var, so the receiver isn't tied to this path specifically. There is a weird way that you can run the agent with no observe agent config file:
- install
- delete the config at the default path
- start the agent using env var overrides for the required fields
but I think that's pretty unlikely and if anyone is doing that, then it's possible that their current app is broken anyway.
Description
OB-42646 Remove all receiver references to bundled config fragments. These files are going away in favor of adding them to the agent binary.